/config/system/interface/<intf_name>/rxFlowControl¶
Ethernet flow control receive operation.
Use
Generally, we recommend leaving flow control off for both receive and send, unless you have a specific reason to turn it on.
Turning on flowcontrol receive tells the port to honor the pause frame from a sending interface. Leaving flow control off tells the interface to ignore the pause frame from the sending interface.
Note: The system supports flow control only on ix interfaces. Flow control is off by default on ix interface types. For other interfaces, the default varies based on the interface type.
Caution: Turning on flowcontrol receive could stop all traffic on the interface.
For a port channel:
- Any flow control setting configured on an interface remains in effect when you add the interface to a port channel.
- You cannot configure flow control on a port channel.
Parameters¶
intf_name: Name of interface
Data Key¶
The data key contains one of the values defined below in Data Values.
Data Type¶
uint32
Default Data Value¶
2 (interface default)
Default Allowed¶
False
Request Methods¶
GET, PUT
Examples¶
GET
curl -b cookie.jar -k https://10.1.2.3:8443/lrs/api/v1.0/config/system/interface/em1/rxFlowControl
GET Response
{"/config/system/interface/em1/rxFlowControl": {"data": 2,
"default": False,
"defaultAllowed": False,
"deleteAllowed": False,
"numChildren": 0,
"type": "uint32"},
"httpResponseCode": 200,
"recurse": False,
"requestPath": "/config/system/interface/em1/rxFlowControl"}
PUT
curl -b cookie.jar –data @data.json -k -H “Content-Type: application/json” -X PUT https://10.1.2.3:8443/lrs/api/v1.0/config/system/interface/em1/rxFlowControl
PUT Response
{"httpResponseCode": 200,
"requestPath": "/config/system/interface/em1/rxFlowControl",
"recurse":false}
- /config/system/interface/<intf_name>/rxFlowControl
1. Parameters
2. Data Key
- Data Type
- Data Values
- Default Data Value 3. Default Allowed 4. Request Methods 5. Related 6. Examples